System and method for managing  dual connectivity with dynamic anchor cell selection

ABSTRACT

Aspects of the subject disclosure may include, for example, obtaining configuration update messages received from neighbor cells of a serving cell of a wireless network, wherein the configuration update messages include dual connectivity capability information of the neighbor cells. The neighbor cells are ranked according to the dual connectivity capability information resulting in a dual connectivity ranking. A target cell of the neighbor cells is selected according to the dual connectivity ranking and a dual connectivity capability of a mobile device, and a dual connectivity service is established according to the dual connectivity ranking. The dual connectivity service includes exchanging user plane messages between the mobile device, a master cell and a secondary cell of the wireless network. Other embodiments are disclosed.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.16/443,015, filed Jun. 17, 2019, which is a continuation of U.S.application Ser. No. 15/658,625, filed on Jul. 25, 2017 (now U.S. Pat.No. 10,368,253), which are incorporated herein by reference in theirentirety.

FIELD OF THE DISCLOSURE

The subject disclosure relates to a system and method for managing dualconnectivity with dynamic anchor cell selection.

BACKGROUND

Dual connectivity (DC) within a wireless mobile scenario, allows mobileuser equipment to exchange user data simultaneously with more than onedifferent base stations. For example, in 3^(rd) Generation PartnershipProject (3GPP) Long Term Evolution (LTE) networks, the mobile userequipment can be configured to support mobile operation of similar ordifferent kinds. For example, mobile user equipment configured tosupport both LTE and Wi-Fi, or both LTE and 5G New Radio (NR), or anycombination of LTE, 5G NR, Wi-Fi, or the like, may be configured by thenetwork to utilize more than one of these links simultaneously.

Beneficially, DC can significantly improve per-user throughput andmobility robustness by allowing the mobile user equipment to beconnected simultaneously to a master cell group and a secondary cellgroup, e.g., via a Master eNodeB (MeNB) and a secondary eNB (SeNB). Theincrease in per-user throughput can be achieved by aggregating radioresources from at least two eNBs. In at least some applications,coordination between participating base stations, e.g., the MeNBs andSeNBs in support of DC operation, can be achieved over existinginterfaces, such as the 3GPP LTE Xn/X2 interface. More generally, DC canbe achieved using different wireless access points having the same ordifferent capabilities, such as eNBs, NodeBs, Wi-Fi, and the like.

As mobile networks evolve towards future trends, such as 3GPP 5G NR (NewRadio) capabilities, it is envisioned that introduction will start withgeographically limited 5G coverage, e.g., hot spots, to support highthroughput using 5G, while relying on the legacy LTE network to providean underlay coverage and reliability. In all likelihood, LTE networkswill co-exist with 5G for a long time. In early stage of 5G NRdeployment, 5G NR may be connected to or otherwise in communication withan LTE core system. It is conceivable that in later stages ofdeployment, LTE cells could be migrated to 5G Next Generation Core(NGC). In either case, UE with LTE and 5G capabilities, e.g., multipleradios, maintains single control plane (CP) connection to the mobilitycore network, and single or dual User Plane (UP) connection to themobility core network.

LTE-5G NR Dual Connectivity enables new UE to connect to both LTE and5G—achieve high throughput via 5G NR and maintain the coverage andreliability by anchoring the signaling (control plane) in LTE. DC canalso minimize control plane signaling load to the core network. With thenetwork evolving to 5G, the surrounding LTE macro cells can be ofvarious conditions—some are suitable to be LTE anchor cell for DC, someare not.

BRIEF DESCRIPTION OF THE DRAWINGS

Reference will now be made to the accompanying drawings, which are notnecessarily drawn to scale, and wherein:

FIG. 1 depicts an illustrative embodiment of a wireless mobility networkemploying a dual connectivity solution;

FIG. 2 depicts an illustrative embodiment of an example of an eNB;

FIG. 3 depicts an illustrative embodiment of a neighbor relations tableto facilitate management of neighbor relations;

FIG. 4 depicts an illustrative embodiment of an LTE Xn/X2 messageexchange to facilitate implementation of dual connectivity solutions;

FIGS. 5A-5B depicts illustrative embodiments of portions of wirelessmobility networks employing dual connectivity solutions;

FIGS. 6-7 depicts illustrative embodiments of processes used in portionsof the system described in FIGS. 1-5B;

FIG. 8 depict illustrative embodiments of communication systems thatprovide media services in portions of the systems described in FIGS.1-5B;

FIG. 9 depicts an illustrative embodiment of a web portal forinteracting with the communication systems of the systems described inFIGS. 1-5B and 8;

FIG. 10 depicts an illustrative embodiment of a communication device forinteracting with the communication systems of the systems described inFIGS. 1-5B and 8; and

FIG. 11 is a diagrammatic representation of a machine in the form of aprocessing system including a process within which a set ofinstructions, when executed, may cause the processor to perform any oneor more of the processes described herein.

DETAILED DESCRIPTION

The subject disclosure describes, among other things, illustrativeembodiments for determining a suitability, rating and/or ranking of awireless access node of a mobile cellular communications network withrespect to dual connectivity (DC) services, in which mobile userequipment exchanges user data with multiple wireless access nodescontemporaneously. A serving node of the cellular network maintains theDC rankings of neighboring nodes and selects a DC master node based onthe rankings. DC services are established in coordination with thetarget node as a DC master node, and another wireless access point, notnecessarily included in the group of neighbor nodes, as a secondarynode. In at least some embodiments, the master node is an eNB of a 3GPPLTE system and the secondary node is a 3GPP 5G NR node. Otherembodiments are described in the subject disclosure.

One or more aspects of the subject disclosure include a system, having aprocessing system including a processor and a memory that storesexecutable instructions. The instructions, when executed by theprocessing system, facilitate performance of operations. The operationsinclude determining a number of dual connectivity ratings for a numberof neighbor cells of a serving cell of a mobile cellular network. A dualconnectivity capability is identified of a mobile communication devicethat engages in wireless communications coordinated by the serving cell.A target cell of the number of neighbor cells is identified based on adual connectivity rating of the number of dual connectivity ratings.Initiation of a dual connectivity service is facilitated based on themobile communication device via the target cell, wherein the target cellserves as a master cell of the dual connectivity service, and whereinthe dual connectivity service comprises exchanging user plane messagesbetween the mobile communication device, the master cell and a secondarycell of the mobile cellular network.

One or more aspects of the subject disclosure include a process thatincludes determining a number of dual connectivity rankings for a numberof neighbor cells of a serving cell of a mobile cellular network. A dualconnectivity capability is determined of a mobile device that engages inwireless communications coordinated by the serving cell. A target cellof the number of neighbor cells is identified based on a dualconnectivity ranking of the number of dual connectivity rankings.Initiation of a dual connectivity service is facilitated based on themobile device via the target cell, wherein the target cell serves as amaster cell of the dual connectivity service, and wherein the dualconnectivity service comprises exchanging user plane messages betweenthe mobile device, the master cell and a secondary cell of the mobilecellular network.

One or more aspects of the subject disclosure include machine-readablestorage medium, including executable instructions that, when executed bya processing system including a processor, facilitate performance ofoperations. The operations include determining dual connectivity valuesfor neighbor cells of a serving cell of a wireless network. A dualconnectivity capability is determined of a wireless device that engagesin wireless communications coordinated by the serving cell. A targetcell of the neighbor cells is determined based on a dual connectivityvalue of the dual connectivity values. Initiation of a dual connectivityservice is facilitated based on the wireless device via the target cell,wherein the target cell serves as a master cell of the dual connectivityservice, and wherein the dual connectivity service includes exchanginguser plane messages between the wireless device, the master cell and asecondary cell of the wireless network.

When DC UE runs a DC friendly application, such as eMBB, it can bedesired to enable DC for the UE. When DC UE moves around and needs toswitch anchor cell, it can be best to be handed over to the DC capableneighbor, otherwise the performance may degrade. To facilitate suchoptimal anchor cell selection, the serving cell may need to know thecapability of neighbor cell. One or more of the exemplary embodiments,can provide mechanisms to dynamically prioritize and select preferredLTE anchor cell for LTE-5G NR dual connectivity operation.

FIG. 1 depicts an illustrative embodiment of an example wirelessmobility system or network 100 adapted for dual connectivityapplications. The system 100 includes a first or primary connectivitycell, e.g., an LTE cell, LTE₁, 102 a, having a first wireless accesspoint, e.g., an LTE base station, e.g., eNB 104 a, a second primaryconnectivity cell, e.g., another LTE cell, LTE₂, 102 b having a secondbase station, e.g., eNB 104 b, and a third primary connectivity cell,e.g., yet another LTE cell, LTE₃, 102 c having a third base station,e.g., eNB 104 c. The LTE cells 102 a, 102 b, 102 c, generally 102,provide wireless service to mobile user equipment, e.g., user equipment(UE) 106, within their respective wireless coverage regions orfootprints. according to LTE disclosed in 3GPP standards, e.g., thevarious 3GPP LTE standards of release 12, or later, incorporated hereinby reference in their entireties.

The system 100 further includes a first alternative connectivity cell,e.g., a 5G connectivity cell 5G₁, 108 a, having a first wireless accesspoint (WAP), e.g., WAP 110 a, and a second alternative connectivitycell, e.g., a second 5G connectivity cell, 5G₂, 108 b having a secondWAP, e.g., 110 b. The 5G cells 108 a, 108 b, generally 108, are alsoadapted to provide wireless service to mobile user equipment, e.g., UE106, within their respective wireless coverage regions or footprints.

Overlapping cells 102, adjacent cells 102 and/or non-adjacent cells 102proximal to each other, e.g., within a particular locality or region,can be referred to as neighboring cells 102. UEs 106 receiving wirelessservice via the mobile cellular network 100, establish radio link withone or more of the eNBs 104 a, 104 b, 104 c, generally 104, sometimesreferred to as the “air interface.” The radio link typically includes anuplink portion, referring to messages directed from the UE 106 towardsthe eNB 104, and a downlink portion, referring to messages directed fromthe eNB 104 towards the UE 106. For LTE applications, the air interfaceemploys a Radio Resource Control (RRC) protocol. The RRC protocol isused in a layer that exists at the IP level between UE 106 and eNB 104.Examples of RRC protocols include, without limitation, a UMTS RRCprotocol specified, e.g., by 3GPP in TS 25.331, Rel. 12 or later, and anLTE RRC protocol specified, e.g., by 3GPP in TS 36.331, Rel. 12 orlater, each of which is incorporated herein by reference in itsentirety. RRC messages can be transported via a Packet Data ConvergenceProtocol (PDCP), e.g., specified by 3GPP in TS 25.323, Ver. 12 or later,for UMTS and TS 36.323 for LTE, Ver. 12 or later, each of which isincorporated herein by reference in its entirety.

As disclosed herein, reference to primary cells refer to so-calledmaster cells of a DC configuration. An eNB 104 of a primary or mastercell 102 can terminate a wireless link to the UE 106, e.g., according toa first radio access technology, e.g., 3GPP LTE access technology. Userdata, such as user packets, can be exchanged by way of an establishedbearer, e.g., a standard bearer, and/or a specialty bearer, e.g., havinga quality of service (QoS) and/or other features adapted to facilitate aparticular service or application, such as voice, video, data, and thelike.

Likewise, reference to secondary cells refer to so-called secondarycells of a DC configuration. A WAP 110 of a secondary cell 108 canterminate a wireless link to the UE 106, e.g., according to the firstradio access technology, and/or a second radio access technology, e.g.,a different 3GPP access technology and/or a non-3GPP access technology.User data, such as user packets, can be exchanged between the UE and theeNB 104 and/or WAP 110 by way of an established bearer, e.g., a defaultbearer, and/or a dedicated bearer, e.g., having a quality of service(QoS) and/or other features adapted to facilitate a particular serviceand/or application, such as voice over IP (VoIP), video, data, and thelike.

It is understood that, in general, a network configuration can includeany number of cells 102, 108, operating in one or more of licensedfrequency spectra, e.g., LTE, unlicensed spectra, e.g., Wi-Fi and/or 5GNR, and the like. It is further understood that neighboring cells 102,108 can provide wireless coverage footprints, or cell sizes, that areoverlapping, adjacent, and/or separated from each other. The extent,e.g., range, shape, location, etc., of the example cells 102, 108 aremerely illustrative. It is understood that one or more of the cells 102,108 can have different shapes, e.g., sectors and that one or more of thecells 102, 108 may be adjacent, overlapping and/or isolated from othercells 102. It is understood further that cell sizes e.g., ranges, can beequal or different. In the illustrative example, the small cells 108 a,108 b, generally 108 fall within the wireless coverage footprints ofrespective LTE cells 102. Coverage footprints of the small cells 108 canbe located entirely within the coverage footprints of the LTE cells 102,as illustrated, or they can straddle edges of the coverage footprints ofthe LTE cells 102, or they can be located external to the coveragefootprints of the LTE cells 102, or any combination thereof.

In DC applications one or more bearers can be split over one or moredifferent eNBs 104 and or WAPs 110. Namely, a single mobile equipment,e.g., UE 106, can consume radio resources provided by at least twodifferent network points, e.g., one or more different eNBs 104 and orWAPs 110. A master cell group includes a group of serving cellsassociated with a master eNB (MeNB). In DC applications, a master eNBterminates at least one S1-MME with a mobile core network, such as anevolved packet core (EPC) 130 of an LTE network. Accordingly, the MeNBacts as a mobility anchor towards the EPC 130. In other words, the MeNBcan facilitate handovers of the UE 106 to one or more other MeNB of themaster cell group. Handovers include, without limitation, a transfer ofradio access technology link from one eNB to another, which may resultfrom one or more scenarios, such as network traffic and/or congestion,licensed spectrum traffic and/or congestion, equipment states, such asprocessing capacity, memory capacity, maintenance, and/or error status.

Likewise, In DC applications, a secondary eNB (SeNB) is an eNB thatprovides additional radio resources for the UE 106, which is not theMeNB. This can include one or more of the eNBs 104 and/or one or more ofthe WAPs, e.g., the 5G WAPs 110. In at least some embodiments, there isan interface between the MeNB, e.g., eNB 104, and the SeNB, e.g., 5G WAP110. According to an example E-UTRAN architecture, the interface caninclude an “Xn” interface, e.g., an X2 interface allowinginterconnections between two gNBs or one gNB and one eLTE eNB. Moregenerally, as used herein, “Xn” or “Xn/X2” can refer to connectionsbetween any combinations of gNB and eNB, including two eLTE eNBs.Example X2 interfaces 112 a, 112 b, 112 c, generally 112, areillustrated between the eNBs 104. Another example interface 114 a, e.g.,an Xn or and Xn/X2 interface is provided between the first eNB 104 a andthe first 5G-WAP 110 a. Likewise, another example Xn/X2 interface 114 bis provided between the second eNB 104 b and the second 5G-WAP 110 b. Itis understood that in at least some embodiments, any one of the 5G-WAPs110 can interface with any one or more of the eNBs 104. Alternatively orin addition, at least some of the 5G-WAP 110 engaging in DC operations,e.g., as SeNB, can do so without necessarily having an interface withany one of the MeNB 104.

Although the example interfaces 112, and 114 a, 114 b, generally 114,are shown as existing between one or more of the eNBs 104 and/or 5G-WAPs110, it is understood that they may instead terminate at another networklocation, such as an up-stream node, e.g., between the eNB 104, 5G-WAP110 and a respective core network, e.g., EPC 130.

The mobile user equipment, e.g., UE 106, can include, withoutlimitation, mobile communication devices, such as mobile telephones,smart phones, laptop computers, desktop computers, tablet devices, andthe like. In at least some embodiments, one or more of the mobile userequipment can include other devices, such as any IP enable device.Examples of IP enabled devices can include, without limitation, homesecurity systems, home security system components, audio and/or videomonitors, appliances, vehicles, smart meters, and the like. By way ofillustrative example, mobile user equipment can include any deviceadapted for operation according to machine-type communications (MTC),e.g., according to the so-called Internet of Things (IoT). Although theterm mobile user equipment is used, it is understood that one or more ofthe UEs 106 can include immobile equipment, such as fixed installationdevices, e.g., home security systems, large devices, e.g., homeappliances, such as washing machines, refrigerators, and so on.

LTE DC is often configured for low to medium mobility speed cases,supporting indoor and/or outdoor, ideal and/or non-ideal backhaulscenarios. Traditionally, LTE DC can be deployed in one of severaldifferent scenarios. For example, the aggregated serving cells of theinvolved eNBs 104 can be intra-frequency or inter-frequencies, and/orthe cell coverage can be overlapping or non-overlapping. In a firstscenario, sometimes referred to as a co-channel scenario, the eNB 104and a small-cell WAP, operate on the same channel Examples include,without limitation, femtocell coverage of a location within a macro cellwhereby both the macro cell and femtocell operate on the same channel.In another scenario, sometimes referred to as an inter-frequencyscenario, the eNB 104 operates on a different channel from thesmall-cell WAP. Examples include, without limitation, small cellcoverage, e.g., picocell or femtocell coverage, of a location within amacro cell, whereby both the macro cell and femtocell operate ondifferent frequencies or channels. In yet other scenarios, sometimesreferred to as small-cell-out-of-coverage-of-macro-cell scenarios, thesmall cell coverage falls outside of a macro cell. The small cell andmacro cell can operate on the same and/or different channels, frequencybands, licensed, unlicensed, and the like.

In 5G NR applications, DC can take on additional dimension(s) of 5Gcoverage alone or in combination with other wireless mobile coverage,e.g., LTE 4G coverage. Consider one or more of the macro cells 102 inthe foregoing examples as either LTE cells or 5G cells. Alternatively orin addition, consider one or more of the small cells 108 in theforegoing examples as 5G cells.

In homogeneous deployments, most or all of the cells provide similarcoverage, e.g., all/most are macro or all/most are small cell. Inheterogeneous deployments cells of different size are employed. In atleast some configurations, the cells are overlapped, e.g., macro andsmall cells, as in the illustrative example of FIG. 1.

The cells in the foregoing scenarios can be classified into primarycells and secondary cells. A primary cell operates on the primaryfrequency in which the UE 106 either performs the initial RRC connectionestablishment procedure or initiates the RRC connection re-establishmentprocedure, or the cell 104 indicated as the primary cell in a handoverprocedure. In at least some embodiments, a secondary cell 104 canoperate on a secondary frequency, which may be configured once an RRCconnection is established and which may be used to provide additionalradio resources.

In at least some embodiments, one of the cells, e.g., the macro cell102, provides an “anchor carrier,” which provides the UE 106 with arobust wide-area signaling connection, carrying system information,basic radio resource control (and potentially low rate or highreliability user data). The small cell, e.g., a 5G NR cell 108 providesanother carrier, which can support an efficient delivery of user trafficwithin its local cell coverage area 108. The anchor carrier 104 aensures that the UE 106 has a reliable signaling connection, e.g., formessage forwarding of a control plane, as it moves around a networkcoverage area, but traffic, e.g., at least a portion of messageforwarding of a user plane, can be offloaded to a local 5G carrier 110.Such offloading can occur, e.g., if a user requires a period of intensecommunication, high bandwidth, low latency, and the like. At least someapplications and/or services can be identified as being well-suited forsuch offloading. Examples include, without limitation, applicationsand/or services that require a relatively large bandwidth and/or arelatively low latency, and/or a relatively high reliability.Applications and/or services including video content offer at least onesuch category that is well suited for offloading.

A distributed radio access node (dRAN) architecture separates a radiofunction unit, e.g., sometimes referred to as a remote radio head (RRH),from the digital function unit, or baseband unit (BBU), e.g., by one ormore of fiber, free space optical, microwave, twisted pair, cable, andthe like.

The deployment scenarios in terms of CN-RAN connection can be classifiedinto the following cases: LTE eNB is a master node; NR gNB is a masternode; and eLTE eNB is a master node. The techniques disclosed herein canbe considered as an evolution of eNB that supports connectivity to EPCand NG-Core. The example systems can support inter-RAT handovers betweenNR gNB and (e)LTE eNB.

In other configurations, the 5G-WAPs 110, sometimes referred to as gNBscan serve as anchor cells. For example, the UE 106 can camp on the gNB110, exchanging control plane and user plane messages with a nextgeneration core network 130 of a 5G portion of the mobile network 100.For example, offloading from a gNB 110 to an eNB can be accomplished inanother DC configuration. It is understood that in at least somescenarios, the gNB 110 can serve as mobility anchors, e.g., of a mastergNB (MgNB) group, relying on the eNBs as secondary eNBs (SeNBs) for DCoperation. Rules for initiating DC according to any of the exampleembodiments disclosed herein can be determined by a network serviceprovider, e.g., a mobile network operator, an application and/or mobileservice provider and/or a third party. For example, DC rules can bedetermined by an enterprise network operator and or a mobile serviceoperator. DC rules can be enforced according to logic at the eNB 104and/or gNB 110 level, and/or at another level, such as at the corenetwork 130 and/or at another network location, such as a third-partyserver.

According to the illustrative example network 100, a first eNB 104 a isin communication with a first cell selector 132 a. Alternatively or inaddition, one or more of the other eNBs 104 b, 104 c are incommunication with a respective cell selector 132 b, 132 c. The cellselector(s) 132 a, 132 b, 132 c, generally 132, can implement orotherwise enforce rules and/or logic related to DC operation. Examplesof cell selectors include devices and/or systems adapted to implementselection rules and/or logic as disclosed hereunder. Examples of cellselection rules and/or logic include, without limitation, one or more ofidentifying DC capabilities of the UE 106, determining that the UE 106is within a wireless coverage region of one or more SeNB and/or SgNB,and/or determining whether any DC equipped UE 106 within SeNB/SgNBcoverage is utilizing and/or likely to utilize an application and/orservice adapted for DC offloading.

According to the illustrative examples, the UE 106 ca include a firstradio system adapted to access LTE radio access technology, and a secondradio system adapted to access 5G NR radio access technology. Althoughdifferent radio systems are disclosed, it is understood that some or allof any particular radio system, e.g., antennas, baseband processors andthe like, can be adapted to facilitate access to more than one radioaccess technologies, e.g., LTE and 5G NR radio access technologies.

One or more of the cell selectors 132 a, 132 b, 132 c can be in furthercommunication with one or more of a number of neighbor relations tables134 a, 134 b, 134 c, generally 134. In the illustrative example eachcell selector 132 is in communication with a corresponding neighborrelations table 134. It is understood that at least some of the cellselectors 132 and/or the neighbor relations tables 134 can be provide ator in close physical proximity to a respective eNB 104 and/or gNB 110.Alternatively or in addition, one or more of the cell selectors 132and/or the neighbor relations tables 134 can be physically separatedfrom a respective eNB 104 and/or gNB 110. Examples of physicalseparation include locating the cell selectors 132 and/or the neighborrelations tables 134 at an up-stream location, e.g., at a physicaland/or network location between the eNB 104 and/or the gNB 110 and acorresponding core network 130. Alternatively or in addition, the cellselectors 132 and/or the neighbor relations tables 134 can be located atthe core network 103, at a data center associated with the mobilenetwork operator and/or at any arbitrary physical and/or networklocation, such as a location of a third party supporting DC operation.

The neighbor relations tables 134 can include, without limitation,identification of a MeNB 104 and/or MgNB 110, as the case may be, e.g.,a cell identifier (cell ID) as a unique value to identify each eNB/gNB,alone or in combination with identifiers of neighboring eNBs 104 and/orneighboring gNBs 110. For example, in at least some embodiments, foreach cell that the eNB 104/gNB 110 has, the eNB 104/gNB 110 maintains aneighbor relations table 134. For each neighbor relation, the neighborrelations table 134 includes a Target Cell Identifier (TCI) thatidentifies a target cell. By way of example for E-UTRAN, the TCIcorresponds to an E-UTAN Cell Global Identifier (ECGI) and Physical CellIdentifier (PCI) of the target cell. In at least some embodiments, theneighbor relations table includes one or more additional attributes asdescribed further hereinbelow.

In at least some embodiments, the system 100 includes a configurationserver 136. The configuration server 136 can be owned, operated and/ormaintained by the mobile network operator and/or by arrangement withanother third party entity on behalf of the mobile network operator. Insome embodiments, the configuration server 136 is in communication withone or more of the eNB 104 and/or gNB 110. Alternatively or in addition,the configuration server 136 is in communication with one or more of thecell selectors 132 and/or the neighbor relations tables 134.

FIG. 2 depicts an illustrative embodiment of an example of an eNB 202,such as the eNBs 104 (FIG. 1). The eNB 202 includes a radio moduleadapted to engage in wireless communications with user equipment, e.g.,a UE 201, over an air interface 203. In the illustrative example, theeNB 202 is adapted for 3GPP LTE operation. The radio module can includea radio resource control (RRC) module 208 adapted to facilitate one ormore radio functions, such as connection establishment and/or releasefunctions, broadcast of system information, radio bearer establishment,reconfiguration, release, mobility procedures, and the like.

The eNB 202 further includes an automatic neighbor relation (ANR)function module 204. In at least some embodiments, the ANR functionmodule 204 is in further communication with a neighbor relations table216. The neighbor relations table 216 can be stored locally at or withinthe eNB 202. Alternatively or in addition, the neighbor relations table216 can be stored at another location physically separated from the eNB202. In more detail, the ANR function module 204 is adapted to managethe neighbor relations table 216. By way of illustrative example,management of the neighbor relations table 216 can include one or moreof adding neighbors, removing neighbors, associating and/or updatingneighbor attributes, and the like.

The example ANR function module 204 includes a neighbor removal functionmodule 212 and/or a neighbor decision module 214. The neighbor removalfunction module 212 and/or the neighbor decision function module 214 canbe in communication with the neighbor relation table management module210. In at least some embodiments, the neighbor removal function module212 receives information obtained internally, e.g., within the eNB 202.The neighbor removal function module 212 processes the information anddetermines whether a particular neighbor should be removed from theneighbor relation table 216. To the extent that it is determined that aneighbor should be removed, the neighbor removal function module 212sends a neighbor removal command, NR_(remove) to the neighbor relationtable management function module 210. Upon receiving the NR_(remove)command, the neighbor relations table management function module 210provides a neighbor relations table update NR_(update) to the neighborrelation table 216. In response to the NR_(update), the neighborrelation table 216 is updated to, e.g., remove the identified neighborfrom the neighbor relation table 216.

In at least some embodiments, the neighbor decision function module 214receives information about neighboring cells. This information can beobtained externally, e.g., from the UE 201 via the air interface 203,from an operations and maintenance system 206, and/or directly fromanother neighboring cell, e.g., via an X2 interface. Information from aneighboring cell can be obtained directly from the neighboring cell, orfrom another mutually neighboring cell, e.g., cell B providesmeasurements to cell A about performance of cell C. The neighbordecision function module 214 processes the information and determineswhether a particular neighbor should be added to the neighbor relationtable 216. To the extent that it is determined that a neighbor should beadded, the neighbor decision function module 214 sends a neighbor addcommand, NR_(add) to the neighbor relation table management functionmodule 210. Upon receiving the NR_(add) command, the neighbor relationstable management function module 210 provides a neighbor relations tableupdate NR_(update) to the neighbor relation table 216. In response tothe NR_(update), the neighbor relation table 216 is updated to, e.g.,add the identified neighbor to the neighbor relation table 216.

In at least some embodiments, the eNB 202 receives measurement reportsover the air link 203 from the UE 201. The measurement reports can beunsolicited, e.g., the UE 201 obtains measurements of a newly discoveredneighbor and provides the measurements in the form of a measurementreport to the neighbor decision function module 214. The UE 201 maydiscover a new neighbor, e.g., by roaming into a coverage area of theneighbor cell. For example, the newly discovered neighbor cell caninclude a non-LTE cell, such as a Wi-Fi WAP and/or a 5G-WAP 110 (FIG.1).

Alternatively or in addition, the neighbor decision function module 214can provide a measurement request to the UE 201, e.g., via the RRC 208,over the air link and via a RRC module 205 of the UE 201. The RRC module295, in turn, communicates with a measurement module 203 of the UE 201to initiate the requested measurement. Without limitation, the requestedmeasurement can include one or more measurements of one or more channelsof one or more neighboring UEs. In at least some embodiments, therequested measurement can be directed to a measurement of the requestingeNB 202. Measurements can include one or more of signal presence, signalstrength, channel capacity, QoS, errors, e.g., error rates,synchronization errors, and the like. For UEs 201 equipped with multipleradios and/or capable of operating in different bands and/or accordingto different wireless protocols, the measurements can includemeasurements of any available eNB, e.g., eNB 104 c, 104 b, and/or anyavailable WAP, e.g., 5G-WAP 110 a, 110 b.

In at least some embodiments, the neighbor relation table managementfunction module 210 is in communication with an O&M system 206. Messagesand/or instructions exchanged between the neighbor relation tablefunction module 210 and the O&M system 206 can include a request fromthe O&M system 206 to add and/or update neighbor relations. For example,the neighbor relation table management function module, in response toreceiving an add/update neighbor relations instruction/command from theO&M system 202, generates an NR_(update) message to update the neighborrelation table 216. The NR_(update) message can be based on input fromthe O&M system 206 alone and/or on information obtained from one or moremeasurement reports, e.g., initiated by measurement requests responsiveto the add/update neighbor relations command. In at least someembodiments, the neighbor relation table management function module 210provides a neighbor relations report to the O&M system 206.

FIG. 3 depicts an illustrative embodiment of a neighbor relations table300 to facilitate management of neighbor relations. The example neighborrelations table 300 includes one column 302 including a neighbor cellrelation (NR) reference, e.g., a number. An NR, e.g., from a source cellto a target cell, indicates that an eNB 104 (FIG. 1) controlling thesource cell 102 (FIG. 1) knows the ECGI/CGI and/or Physical CellIdentifier (PCI) of the target cell and has an entry in the neighborrelations table 300 for the source cell identifying the target cell.

Another column 304 includes a target cell identifier (TCI). For eachcell 102 that the eNB 104 has, the eNB 104 keeps an NRT 134 (FIG. 1).For each NR, the neighbor relations table 300 contains the Target CellIdentifier (TCI), which identifies the target cell. For E-UTRAN, the TCIcorresponds to an E-UTAN Cell Global Identifier (ECGI) and/or PhysicalCell Identifier (PCI) of the target cell. One or more additional columnsinclude one or more attributes associated with a particular neighborrelation.

The eNB 104 serving cell 102 equipped with an automatic neighborrelation (ANR) function module 204 (FIG. 2), instructs each UE 201 (FIG.2) to perform measurements on neighbor cells 104, 110, e.g., as a partof a normal call procedure. When the UE 201 discovers a new cell ECGI,the UE 201 reports the detected ECGI to the serving cell eNB 104. In atleast some embodiments, the UE 201 also reports the tracking area codeand all PLMN IDs that have been detected. The eNB 104 adds the newlydiscovered neighbor relation to neighbor relation table 300.

In at least some embodiments, the eNB 104 of the serving cell 102,equipped with an ANR function module 204, can instruct the UE 201 toperform measurements and detect cells on other radio access terminalsand/or other frequencies, e.g., during connected mode. The UE 201reports information, such as PCI, of the detected cells 102, 108 in thetarget radio access terminal and/or frequencies. When the eNB 201receives measurement reports from the UE 201 containing information,such as PCIs of neighboring cell(s), the eNB 202 may instruct the UE 201to read certain information based on the detected neighbor cell,updating its neighbor relation table 216 after receiving relevantinformation from the UE 201.

Example attributes include those defined in 3GPP TS 36.300, rel. 12,including “No Remove,” “No HO,” and “No X2.” For example, the neighborrelations table includes one column 306 to indicate whether a particularNR should be configured with a “no remove” status. No Remove means: Ifchecked, the eNB shall not remove the neighbor cell relation from theneighbor relation table when running a function to remove aged NRs. Sucha status would prevent an associated NR from being removed from theneighbor relation table 300, regardless of any command, network and/orequipment condition. Likewise, another attribute includes another column308 to indicate whether a particular NR should be configured with a “nohandover (HO)” status. Such a status would prevent an associated NR frombeing handed over, when so indicted in the neighbor relation table 300,regardless of any commands, requests, network and/or equipmentcondition(s). Yet another attribute includes another column 310 toindicate whether a particular NR does not have an X2 interface, or anexisting X2 interface should not be used. Such a status would prevent anassociated NR from accessing/using an X2 interface, and/or alert the ANRfunction module 304 that an X2 interface is not available, when soindicted in the neighbor relation table 300, regardless of any commands,requests, network and/or equipment condition.

According to the techniques disclosed herein, another attribute includesa column 312 to indicate a DC preference, rank, capability, or the like.It is understood that NRs can involve equipment, such as eNBs 104 and/orgNBs 110 having different configurations and/or capabilities. In someinstances a target cell of a particular NR may not be configured orotherwise adapted to support DC functions. In such instances, the DCpreference entry can include a value indicative of no DC support. Thevalue can include an alphanumeric value, a binary value, or any othersuitable character or value, including a null value. It is understoodthat at least some of the eNBs 104 and/or gNBs 110 having one or moreconfigurations and/or capabilities that support DC functions. In someinstances a first target cell of a particular NR may be configured orotherwise adapted to support DC functions by way of a firstconfiguration. The illustrative example includes three levels of DCpreference, e.g., “preferred,” “fallback” and “no support.” It isunderstood that a greater and/or fewer number of levels of DC preferencecan be used.

Likewise, a second target cell of the NR may be configured or otherwiseadapted to support DC functions by way of a second configuration.Depending upon the particulars of the different configurations, thefirst configuration may be more or less preferable than the secondconfiguration. Accordingly, the DC preference entry can include one ormore values indicative of the particular configuration and/or a relativepreference, ranking, capability, or the like. In such instances, the DCpreference entry can include a value indicative of no DC support. Thevalue can include an alphanumeric value, a binary value, or any othersuitable character or value, including a null value.

In at least some embodiments, one or more of the neighbor relationattributes, e.g., columns 306, 308, 310, 312, can be controlled by anO&M system 206 (FIG. 2). For example, the O&M system 206 can set certainattributes, such as no remove, no HO and/or no X2 according to systemmanagement preferences, hardware and/or network requirements, and thelike. Alternatively or in addition, the O&M system 206 can set certainattributes of the DC preference. In at least some embodiments, the DCpreferences are set according to configuration and/or capability of atarget cell of the associated NR 302. Configurations and/or capabilitieswould generally be known to the O&M system 206. However, in at leastsome embodiments, it is understood that a value of the DC preferencecolumn 312 can be set and/or changed according to other means. Forexample, a target cell may self-report its configuration and/orcapabilities, e.g., over an X2 interface with a serving cell.Alternatively or in addition, a neighbor cell, e.g., including theserving cell, may determine and/or otherwise infer a configurationand/or capability of the target cell.

FIG. 4 depicts an illustrative embodiment of an LTE X2 message exchange400 to facilitate implementation of dual connectivity solutions. The X2Application Protocol (AP) is used to handle UE mobility within E-UTRANand provides one or more of the following functions: mobilitymanagement; load management; reporting of general error situations,resetting the X2, setting up the X2, and/or eNB configuration updates.The illustrative example includes a first X2-AP message based on an eNBConfiguration Update function. An example eNB configuration updatemessage is disclosed in 3GPP TS 36.423, section 8.3.5. This message issent by an eNB to a peer eNB to transfer updated information. The eNBConfiguration Update function allows updating of application level dataneeded for two eNBs 406, 408 to interoperate correctly over an X2interface.

The example X2-AP eNB Configuration Update message is exchanged betweena first eNB_A 406 and a second, peer eNB_B 408. Upon receipt of themessage 402, eNB_B 408 updates the information for eNB_A 406. The secondeNB_B 408 replies with an X2-AP: eNB Configuration UpdateAcknowledgement message 404 to inform the initiating eNB_A 406 that therequested update of application data was performed successfully.

The example X2-AP protocol eNB Configuration Update message 402 caninclude any of the traditional information elements generally known tobe associated with the message in addition to another informationelement (IE) directed to DC preference. An example of a Served CellInformation IE of an eNB Configuration Update message is disclosed 3GPPTS 36.423, section 9.2.8. In at least some embodiments, an LTE-5G NR DCPreference IE can be added to the existing message, e.g., as a field ofServed Cell Information IE. The DC Preference IE can include anindication of the preference disclosed above in the example neighborrelation table 300 (FIG. 3). Namely, the DC Preference IE can includethe particular value to be included in the DC preference column 312 ofthe neighbor relation table 300. Alternatively or in addition, the DCpreference IE can include a value suggestive of and/or that, whensubject to analysis and/or interpretation can provide an indication ofthe DC preference value to be included in the DC preference column 312of the neighbor relation table 300.

FIGS. 5A-5B depicts illustrative embodiments of portions of wirelessmobility networks 500, 550 employing dual connectivity solutions.According to a first illustrative example of FIG. 5A, the systemincludes a split radio access node (RAN) 500. For example, the split RANincludes PDLC/RLC non real-time function module(s) that can be split andmoved to another geographic and/or network location that is physicallyseparate from the base station, e.g., eNB, and/or gNB. The split RANsystem includes a MeNB 504 and a SgNB 518. The MeNB 504 includes a firstPDCP_(LTE) module 508 a and a second PDCP_(LTE) module 508 b, a firstRLC_(LTE) module 510 a and a second RLC_(LTE) module 510 b, and aMAC_(LTE) module 512. A lower portion of the example split RAN node 500,including the MAC_(LTE) module 512 serves as a distributed unit, e.g.,being location at the MeNB. An upper portion serves as a remote, e.g., acentralized portion of the example split RAN node 500, including thePDCP_(LTE) modules 508 a, 508 b and the RLC_(LTE) modules 510 a, 510 b.The upper or centralized portion is in communication between thedistributed portion and an evolved packet core (EPC) 514. A first mastercell group bearer(s) is processed by the first PDCP_(LTE) 508 a, thefirst RLC_(LTE) 510 a and the MAC_(LTE) 512. Likewise, a separate butrelated and/or a split bearer is processed by the second PDCP_(LTE) 508b, the second RLC_(LTE) 510 b and the MAC_(LTE) 512.

According to a DC service established between the MeNB 504 and the SgNB506, user data associated with the separate but related and/or splitbearer are exchanged between the second PDCP_(LTE) 508 b and an RLC_(NR)516 of the SgNB 506. The SgNB 506 further includes a MAC_(NR) 518 tofacilitate processing of the separate/split bearer data packetsaccording to DC services. Beneficially, the same UE 502 exchangescontrol messages via the MeNB 504, e.g., related to mobility,establishment of DC services, and the like. The same UE 502contemporaneously exchanges data messages via the SgNB 506 according toDC services. For applications using 5G NR, the user message bandwidth isexpected to be substantially greater than otherwise available using LTE.Accordingly, user data messages can be selectively processed by the SgNB506 according to a DC service established by the MeNB 502.

It is worth noting that the foregoing split RAN embodiment 500 is anexample of a so-called, LTE-5G NR DC “preferred” MeNB. The preferencecan be related, at least in part, to an Xn interface connectscentralized PDCP/RLC 508 b, 510 b, independent of LTE anchor cell RLC510 a/lower layer capability and location.

According to a second illustrative example of FIG. 5B, the system 550includes a radio access node (RAN), e.g., an MeNB 554 that is not split,as in the previous example. For example, the MeNB 554 includes aPDLC/RLC non real-time function module(s). Once again, the system 550includes a MeNB 554 and a SgNB 556. The MeNB 554 includes a firstPDCP_(LTE) module 558 a and a second PDCP_(LTE) module 558 b, a firstRLC_(LTE) module 560 a and a second RLC_(LTE) module 560 b, and aMAC_(LTE) module 562. A lower portion of the example split RAN node 560,including the MAC_(LTE) module 512 serves as a distributed unit, e.g.,being location at the MeNB, together with an upper portion, includingthe PDCP_(LTE) modules 558 a, 558 b and the RLC_(LTE) modules 560 a, 560b. The upper portion is in communication between the lower portion andan evolved packet core (EPC). A first EPS bearer 570 is processed by thefirst PDCP_(LTE) 558 a, the first RLC_(LTE) 560 a and the MAC_(LTE) 562.Likewise, a separate but related and/or a split bearer is processed bythe second PDCP_(LTE) 558 b, the second RLC_(LTE) 560 b and theMAC_(LTE) 562.

According to a DC service established between the MeNB 554 and the SgNB556, user data associated with the separate but related and/or splitbearer are exchanged between the second PDCP_(LTE) 558 b and an RLC_(NR)566 of the SgNB 556. The SgNB 556 further includes a MAC_(NR) 568 tofacilitate processing of the separate/split bearer data packetsaccording to DC services. Beneficially, the same UE 552 exchangescontrol messages via the MeNB 554, e.g., related to mobility,establishment of DC services, and the like. The same UE 552contemporaneously exchanges data messages via the SgNB 556 according toDC services. For applications using 5G NR, the user message bandwidth isexpected to be substantially greater than otherwise available using LTE.Accordingly, user data messages can be selectively processed by the SgNB556 according to a DC service established by the MeNB 552.

It is worth noting that the foregoing non-split RAN embodiment 550 is anexample of a so-called, LTE-5G NR DC “fallback” MeNB. The preference canbe related, at least in part, to an Xn interface that connects thePDCP/RLC 558 b, 560 b.

FIG. 6 depicts an illustrative embodiment of a process 600 used tofacilitate DC service between a 3GPP LTE eNB 104 and a 5G WAP 108 (FIG.1). A capability of a UE 106 (FIG. 1) is determined at 602. Inparticular, the capability is indicative of a DC capability of the UE106. It is understood that DC includes a contemporaneous exchange ofuser data with multiple wireless access points/base stations. Sometimesthe different WAPs/eNBs are on different channels and/or operatingwithin different networks altogether, e.g., LTE vs. 5G. Accordingly, aDC capable UE 106 can include multiple radios, which can be adapted tooperate in different bands and/or according to different wireless accessprotocols.

A determination is made at 604 as to whether the UE 106 is 5G NRcapable. UE capabilities can be determined by any of various techniques.For example, the UE 106 can report or otherwise identify itscapabilities via a message exchange with a serving node of the wirelessnetwork. Alternatively or in addition, the capabilities can bedetermined by a predetermined association, e.g., according to a lookuptable. In such applications, the UE 106 can identify itself, e.g.,according to an equipment type, model number, equipment identification(ID), and the like. The equipment type and/or ID can be used as areference to identify capabilities from another source, such as anetwork operator, an equipment manufacturer, and/or a third partyservice, such as an equipment type repository.

Responsive to determining that UE is not 5G NR capable, the UE stayswith LTE only at 606. It is understood that DC service can beestablished for other network nodes, such as other LTE nodes, Wi-Finodes and the like, despite the UE not being 5G NR capable. Accordingly,the techniques disclosed herein can be applied broadly to any DC serviceconfiguration. The illustrative example merely includes a scenario inwhich DC service is extended from an LTE network node to a 5G NR networknode. It is worth noting that in at least some instances, the techniquesdisclosed herein can be applied in a 5G-5G DC service scenario and/or ascenario in which LTE service is extended from a 5G NR network node toan LTE network node.

Responsive to determining that the UE is 5G NR capable, wirelesscoverage available to UE is determined at 608. For example, a UE 106being served from an eNB 104 receives an indication from the UE 106,e.g., by way of a measurement report, that the UE 106 is within awireless coverage of one or more mobile network nodes, such as eNBs 104and/or 5G-WAPs 110. For example, a DC capable UE 106 can monitor LTEand/or 5G NR frequency bands to identify available services. Theavailability of LTE and/or 5G NR service may change based on one or moreof mobility of the UE 106, network conditions, an operational state ofthe UE 106, and the like.

Availability of 5G NR coverage is determined at 610. This can beaccomplished by receipt of a measurement report from the UE 106indicating that it has detected and/or performed a measurement based onthe 5G NR coverage. Measurements can include any measurements routinelyperformed by the UE 106, e.g., signal strength, signal frequency,channel and/or frequency band, QoS, errors, e.g., bit error rate, errorparity, forward error correction values, and the like.

Responsive to a determination that 5G NR coverage is not available, theUE stays with LTE only at 606. To the extent that other coverage isdetermined, e.g., other LTE eNBs, and/or other WAPs, such as Wi-Fi,Bluetooth, and the like, the techniques disclosed herein can be appliedto establish DC service based on a similar rating, ranking and/orpreference.

Responsive to a determination that 5G NR coverage is available, aservice and/or application associated with the UE is determined at 612.Services can include, without limitation, voice services, e.g., VoIP,video services, e.g., streaming video, data services, and the like. Insome embodiments, the services are active or otherwise pre-establishedvia the serving eNB. Alternatively or in addition, the services can bein a requested state, in which the UE 106 and/or a remote device/systemis requesting access to any such services in association with the UE106.

In at least some embodiments, the service are neither active norrequested. For example, the services can be identified as defaultservices, e.g., based on a level of subscription, an equipment type, apromotion of the network operator and/or service provider, e.g.,NETFLIX®, and the like. Alternatively or in addition, the services canbe identified based on past performance of the particular UE 106, and/orpast performance of a user and/or group of users associated with theparticular UE 106. For example, if a user has used streaming videoservices in the past, it can be determined that the user is likely touse the same or similar services in the future. Accordingly, target eNBscan be identified in association with the UE 106 based on the currentand/or past service requests.

In at least some embodiments, a service profile and/or schedule can bedetermined and associated with the UE 106. The service profile and/orschedule can be based on one or more of a time of day, a day of theweek, a location of the UE 106, an identity of a user of the UE 106,e.g., according to presence data of the user and so on. Consider, by wayof illustrative example, a commuter who routinely uses the YOUTUBE®application while commuting on a train, a bus and the like. It can bedetermined by one or more of a time of day, a day of the week, alocation of the UE 106, and/or a presence of the user whether the useris likely to engage in YOUTUBE® services. To the extent it is determinedthat streaming media service is likely, regardless of whether theservice is active or has been requested, the cell selector 132 (FIG. 1)and/or the ANR function 204 (FIG. 2) can determine the service and/orapplication at 612.

An evaluation of suitability of the identified UE service(s) for DC isperformed at 614. It is understood that some services may be morewell-suited for DC service than others. Namely, provisioning and/ormanagement of DC services involves some measure of overhead. Perhapsmore importantly, provisioning and/or management of DC services mayresult in certain available eNBs as being overlooked or otherwise notinclude as possible targets, e.g., in anticipation for a handover.Accordingly, by restricting the number available target eNBs to onlythose capable of 5G NR services, some measure of flexibility will belost in managing handover events.

Responsive to a determination that UE service(s) is not available forDC, the UE stays with LTE only at 606. This can include DC serviceswithin LTE and/or with other WAPs, such as Wi-Fi, Bluetooth and thelike.

Responsive to a determination that UE service(s) is available for DC, anindication and/or identification of an LTE-5G anchor preference, rating,and/or ranking is determined at 616. In at least some embodiments, theLTE-5G anchor preference can be determined from a neighbor relationstable 134, 216, 300 (FIGS. 1-3). For example, the neighbor relationstable 300 includes a column 312 identifying an LTE-5G NR DC preferencevalue for each of the listed neighbor relations. According to theillustrative examples disclosed herein, the LTE-5G preference value candistinguish among a range of LTE-5G capable target cells and/or amongthose cells that are incapable of LTE-5G DC service.

It is envisioned that for at last some period of time, particular duringan anticipated transition period for implementing 5G NR service, therewill be at least some eNBs that are not 5G-NR capable. Accordingly, suchincapable eNBs can be excluded from consideration when consideringtarget cell(s) for a LTE-5G DC capable UE. Likewise, there may be someeNBs that are better suited than others for LTE-5G DC service. It isunderstood that such variability among LTE-5G DC capable eNBs can beidentified by corresponding entries in column 312 identifying LTE-5G NRDC preference values associated with the different neighbor relations.

In at least some embodiments, logic and/or business rules can bedetermined and/or otherwise applied to identify target eNBs based on oneor more of the associated LTE-5G NR DC preference value(s), the UEcapability(s), the user identity and/or level of subscription, currentand/or past mobile applications and/or services accessed by the UE, andthe like. Accordingly, high bandwidth services, such as streaming video,may take preference when selecting target eNBs, such that “preferred”eNBs will be selected over “fallback” eNBs when both are available asneighbors.

It is further understood that any logic and/or business rules can weighand/or otherwise combine the LTE-5G NR DC preference values 312 withother values, such as other attributes 306, 308, 310 of the neighborrelation table, and/or other considerations, such as QoS, signalstrength, error performance and the like of the available LTE-5G NR DCeNBs and those neighbor cells not equipped to provide such report. Thus,it is conceivable that a neighbor cell that does not support LTE-5G NRDC can be selected over other neighbor cells that do, based on one ormore of currently accessed service(s), network conditions, such asnetwork congestion, network delay, error performance, priorities and thelike.

Availability of the preferred anchor is determined at 620, e.g., basedon application of one or more of the example logic and/or businessrules. Responsive to a determination that the preferred anchor is notavailable, the UE stays with LTE only at 626. Responsive to adetermination that the preferred anchor is available, LTE-5G DC isenabled between preferred anchor and the UE. In at least someembodiments, the foregoing process can continue in a looped fashion,e.g., repeating periodically and/or continuously. Repetition can bescheduled based, e.g., every few seconds, minutes, hours, and the like.Alternatively or in addition, repetition and/or looping can be eventbased, e.g., based on a request for service, establishment of a service,a level of activity associated with a service, network conditions, USmobility, 5G NR availability, and the like.

Families of usage scenarios include, without limitation—enhanced mobilebroadband (eMBB); massive machine type communications (mMTC); andultra-reliable and low latency communications (URLLC). Exampleapplications and/or services can include smart home/building, voice,video, 3D video, augmented reality, education, industrial automation,mission-critical applications, e.g., e-health, transportation, e.g.,self-driving cars, and the like.

By way of example, an initial LTE-5G DC setup includes a UE “camping” inan LTE cell, e.g., a serving LTE cell. The UE sets up a call and reportsUE capability to the serving LTE cell. Presuming that the UE is LTE-5GNR Dual Connectivity capable, the UE moves into 5G NR coverage andreports 5G NR measurement back to the serving LTE cell. If the UE runs aDC “friendly” application, e.g., an application well suited to 5G DC,such as eMBB, the serving LTE cell employs logic and/or business rules,e.g., according to a decision tree to select an LTE anchor cell forLTE-5G DC. It is understood that the LTE anchor cell can include theserving cell, presuming it is LTE-5G capable, and/or any other neighborcells that are LTE-5G DC capable. It is understood that the neighborcell capability/priority to support LTE-5G DC can be dynamicallyupdated, e.g., via X2 message exchanges or neighbor relation tableupdates, e.g., via an Operational Support System (OSS). During an anchorcell handover of LTE operations, the same or similar mechanism can beapplied to select a target LTE anchor cell.

FIG. 7 depicts an illustrative embodiment of an example of a preferredanchor identification portion 618 of the process 600 used to facilitateDC service between a 3GPP LTE eNB 104 and a 5G WAP 108 (FIG. 1).According to the process 618, a determination is made at 708 as towhether the currently serving LTE cell, e.g., an eNB, has a LTE-5G DCanchor preferred attribute. As disclosed herein, the attribute can bedetermined by an entry in a neighbor relations table associated with theserving eNB. To the extent that the serving LTE cell is rated, ranked orotherwise identified as a preferred cell to serve as a LTE-5G DC anchorcell, LTE-5G DC is enable on the UE at 710. According to DC service, asecondary 5G cell is further identified and DC services initiatedbetween the LTE-5G DC anchor cell and the secondary 5G cell.

Further according to the process 618, one or more neighbor cells areidentified at 712 as possible DC target cells. A determination is madeat 714 as to whether the identified neighbor cell(s) provides wirelesscoverage and is identified with a LTE-5G DC attribute as being“preferred.” It is understood that the determination of wirelesscoverage can be made based on measurements, e.g., accomplished by theUE, by one or more other cells, and/or by other devices, e.g., other UE.Wireless coverage can be evaluated based on one or more parameters, suchas signal strength, frequency and/or band, interference, errorperformance, e.g., bit error rate, forward error correction parameters,and the like.

To the extent that it is determined that the identified cell(s) providefavorable wireless coverage and has an LTE-DC rating of “preferred,” theserving cell triggers a UE handover to the identified neighbor cell as atarget cell at 716. DC services can be initiated with the target cellserving as a MeNB and a 5G WAP serving as a SgNB.

Responsive to the identified neighbor cell neither providing adequatewireless coverage nor having a preferred attribute, a determination ismade at 718 as to whether the currently serving LTE cell, e.g., an eNB,has a LTE-5G DC anchor “fallback” attribute. Once again, the attributecan be determined by an entry in a neighbor relations table associatedwith the serving eNB. To the extent that the serving LTE cell is rated,ranked or otherwise identified as a fallback cell to serve as a LTE-5GDC anchor cell, LTE-5G DC is enable on the UE at 720. According to DCservice, a secondary 5G cell is further identified and DC servicesinitiated between the LTE-5G DC anchor cell and the secondary 5G cell.

Further according to the process 618, one or more neighbor cells areidentified at 712 as possible DC target cells. A determination is madeat 722 as to whether any of the identified neighbor cell(s) providewireless coverage and are identified with a LTE-5G DC attribute as being“preferred.” It is understood that the determination of wirelesscoverage can be made based on measurements, e.g., accomplished by theUE, by one or more other cells, and/or by other devices, e.g., other UE.Wireless coverage can be evaluated based on one or more parameters, suchas signal strength, frequency and/or band, interference, errorperformance, e.g., bit error rate, forward error correction parameters,and the like.

To the extent that it is determined that the identified cell(s) providefavorable wireless coverage and has an LTE-DC rating of “fallback,” theserving cell triggers a UE handover to the identified neighbor cell as atarget cell at 721. DC services can be initiated with the target cellserving as a MeNB and a 5G WAP serving as a SgNB.

To the extent that it is determined that the identified cell(s) do notprovide favorable wireless coverage and/or do not have an LTE-DC ratingof “fallback,” LTE-5G DC operation is not available at 726.

While for purposes of simplicity of explanation, the respectiveprocesses are shown and described as a series of blocks in FIGS. 6-7, itis to be understood and appreciated that the claimed subject matter isnot limited by the order of the blocks, as some blocks may occur indifferent orders and/or concurrently with other blocks from what isdepicted and described herein. Moreover, not all illustrated blocks maybe required to implement the methods described herein.

FIG. 8 depicts an illustrative embodiment of a communication system 800for providing various communication services, such as delivering mediacontent. The communication system 800 can represent an interactive medianetwork, such as an interactive television system (e.g., an InternetProtocol Television (IPTV) media system). Communication system 800 canbe overlaid or operably coupled with the wireless mobility communicationsystems of FIGS. 1-5 as another representative embodiment ofcommunication system 800. For instance, one or more devices illustratedin the communication system 800 of FIG. 8 determines dual connectivityvalues for neighbor cells of a serving cell of a wireless network. Adual connectivity capability is determined of a wireless device thatengages in wireless communications coordinated by the serving cell. Atarget cell of the neighbor cells is determined based on a dualconnectivity value of the dual connectivity values. Initiation of a dualconnectivity service is facilitated based on the wireless device via thetarget cell, wherein the target cell serves as a master cell of the dualconnectivity service, and wherein the dual connectivity service includesexchanging user plane messages between the wireless device, the mastercell and a secondary cell of the wireless network.

In one or more embodiments, the communication system 800 can include asuper head-end office (SHO) 810 with at least one super headend officeserver (SHS) 811 which receives media content from satellite and/orterrestrial communication systems. In the present context, media contentcan represent, for example, audio content, moving image content such as2D or 3D videos, video games, virtual reality content, still imagecontent, and combinations thereof. The SHS server 811 can forwardpackets associated with the media content to one or more video head-endservers (VHS) 814 via a network of video head-end offices (VHO) 812according to a multicast communication protocol. The VHS 814 candistribute multimedia broadcast content via an access network 818 tocommercial and/or residential buildings 802 housing a gateway 804 (suchas a residential or commercial gateway).

The access network 818 can represent a group of digital subscriber lineaccess multiplexers (DSLAMs) located in a central office or a servicearea interface that provide broadband services over fiber optical linksor copper twisted pairs 819 to buildings 802. The gateway 804 can usecommunication technology to distribute broadcast signals to mediaprocessors 806 such as Set-Top Boxes (STBs) which in turn presentbroadcast channels to media devices 808 such as computers or televisionsets managed in some instances by a media controller 807 (such as aninfrared or RF remote controller).

The gateway 804, the media processors 806, and media devices 808 canutilize tethered communication technologies (such as coaxial, powerlineor phone line wiring) or can operate over a wireless access protocolsuch as Wireless Fidelity (WiFi), Bluetooth®, Zigbee®, or other presentor next generation local or personal area wireless network technologies.By way of these interfaces, unicast communications can also be invokedbetween the media processors 806 and subsystems of the IPTV media systemfor services such as video-on-demand (VoD), browsing an electronicprogramming guide (EPG), or other infrastructure services.

A satellite broadcast television system 829 can be used in the mediasystem of FIG. 8. The satellite broadcast television system can beoverlaid, operably coupled with, or replace the IPTV system as anotherrepresentative embodiment of communication system 800. In thisembodiment, signals transmitted by a satellite 815 that include mediacontent can be received by a satellite dish receiver 831 coupled to thebuilding 802. Modulated signals received by the satellite dish receiver831 can be transferred to the media processors 806 for demodulating,decoding, encoding, and/or distributing broadcast channels to the mediadevices 808. The media processors 806 can be equipped with a broadbandport to an Internet Service Provider (ISP) network 832 to enableinteractive services such as VoD and EPG as described above.

In yet another embodiment, an analog or digital cable broadcastdistribution system such as cable TV system 833 can be overlaid,operably coupled with, or replace the IPTV system and/or the satelliteTV system as another representative embodiment of communication system800. In this embodiment, the cable TV system 833 can also provideInternet, telephony, and interactive media services. System 800 enablesvarious types of interactive television and/or services including IPTV,cable and/or satellite.

The subject disclosure can apply to other present or next generationover-the-air and/or landline media content services system.

Some of the network elements of the IPTV media system can be coupled toone or more computing devices 830, a portion of which can operate as aweb server for providing web portal services over the ISP network 832 towireline media devices 808 or wireless communication devices 816.

Communication system 800 can also provide for all or a portion of thecomputing devices 830 to function as a neighbor relations manager and/orcell selection server 830. The neighbor relations manager/cell selectionserver 830 can use computing and communication technology to performfunction 862, which can include among other things, the neighborrelations management techniques described by processes 600-700 of FIGS.6-7. For instance, function 862 of the neighbor relations manager/cellselection server 830 can be similar to the functions described for theO&M server 306 of FIG. 3 in accordance with the processes 600-700 ofFIGS. 6-7. The eNBs 817 a, 817 b, generally 817, and evolved packet core840 can be provisioned with software functions 864 and 866,respectively, to utilize the services of neighbor relations manager/cellselection server 830. For instance, functions 864 and 865 of eNBs 817and evolved packet cores 840 can be similar to the functions describedfor the eNBs 104, 112, 120, 204, 254 and/or evolved packet cores 130,214 of FIGS. 1, 2A, 2B in accordance with the processes 600-700 of FIGS.6 and 7.

Multiple forms of media services can be offered to media devices overlandline technologies such as those described above. Additionally, mediaservices can be offered to media devices by way of a wireless accessbase station 817 operating according to common wireless access protocolssuch as Global System for Mobile or GSM, Code Division Multiple Accessor CDMA, Time Division Multiple Access or TDMA, Universal MobileTelecommunications or UMTS, World interoperability for Microwave orWiMAX, Software Defined Radio or SDR, Long Term Evolution or LTE, and soon. Other present and next generation wide area wireless access networktechnologies can be used in one or more embodiments of the subjectdisclosure.

FIG. 9 depicts an illustrative embodiment of a web portal 902 of acommunication system 900. Communication system 900 can be overlaid oroperably coupled with systems 100, 300, 500, 550 of FIGS. 1-2 and/or5A-5B, and/or communication system 800 as another representativeembodiment of systems 100, 300, 500, 550 of FIGS. 1-2 and/or 5A-5B,and/or communication system 800. The web portal 902 can be used formanaging services of systems 100, 300, 500, 550 of FIGS. 1-2 and/or5A-5B, and/or communication system 800. A web page of the web portal 902can be accessed by a Uniform Resource Locator (URL) with an Internetbrowser using an Internet-capable communication device such as thosedescribed in relation to the systems 100, 300, 500, 550 of FIGS. 1-2and/or 5A-5B, and/or communication system 800. The web portal 902 can beconfigured, for example, to access a media processor 806 and servicesmanaged thereby such as a Digital Video Recorder (DVR), a Video onDemand (VoD) catalog, an Electronic Programming Guide (EPG), or apersonal catalog (such as personal videos, pictures, audio recordings,etc.) stored at the media processor 806. The web portal 902 can also beused for provisioning IMS services described earlier, provisioningInternet services, provisioning cellular phone services, and so on.

The web portal 902 can further be utilized to manage and provisionsoftware applications 862-866 to adapt these applications as may bedesired by subscribers and/or service providers of systems 100, 300,500, 550 of FIGS. 1-2 and/or 5A-5B, and/or communication system 800. Forinstance, users of the services provided by the cell selector 134 or theneighbor relations manager/cell selection server 830 can log into theiron-line accounts and provision the servers 110 or the neighbor relationsmanager/cell selection server 830 with logic and/or business rules,e.g., to be applied in association with the techniques disclosed herein.Alternatively or in addition, the web portal 902 can be used to updatemaintenance status, to enter, view and/or otherwise modify configurationparameters, e.g., including associations of LTE-5G DC attributes withone or more of the eNBs and/or 5G gNBs, and so on. Service providers canlog onto an administrator account to provision, monitor and/or maintainthe systems 100, 300, 500, 550 of FIGS. 1-2 and/or 5A-5B, and/orcommunication system 800.

FIG. 10 depicts an illustrative embodiment of a communication device1000. Communication device 1000 can serve in whole or in part as anillustrative embodiment of the devices depicted in FIGS. 1-2 and/or5A-5B and/or FIG. 8, and can be configured to perform portions ofprocesses 600, 700 of FIGS. 6-7.

Communication device 1000 can comprise a wireline and/or wirelesstransceiver 1002 (herein transceiver 1002), a user interface (UI) 1004,a power supply 1014, a location receiver 1016, a motion sensor 1018, anorientation sensor 1020, and a controller 1006 for managing operationsthereof. The transceiver 1002 can support short-range or long-rangewireless access technologies such as Bluetooth®, ZigBee®, Wi-Fi, DECT,or cellular communication technologies, just to mention a few(Bluetooth® and ZigBee® are trademarks registered by the BluetoothSpecial Interest Group and the ZigBee® Alliance, respectively). Cellulartechnologies can include, for example, CDMA-1X, UMTS/HSDPA, GSM/GPRS,TDMA/EDGE, EV/DO, WiMAX, SDR, LTE, as well as other next generationwireless communication technologies as they arise. The transceiver 1002can also be adapted to support circuit-switched wireline accesstechnologies (such as PSTN), packet-switched wireline accesstechnologies (such as TCP/IP, VoIP, etc.), and combinations thereof.

The UI 1004 can include a depressible or touch-sensitive keypad 1008with a navigation mechanism such as a roller ball, a joystick, a mouse,or a navigation disk for manipulating operations of the communicationdevice 1000. The keypad 1008 can be an integral part of a housingassembly of the communication device 1000 or an independent deviceoperably coupled thereto by a tethered wireline interface (such as a USBcable) or a wireless interface supporting for example Bluetooth®. Thekeypad 1008 can represent a numeric keypad commonly used by phones,and/or a QWERTY keypad with alphanumeric keys. The UI 1004 can furtherinclude a display 1010 such as monochrome or color LCD (Liquid CrystalDisplay), OLED (Organic Light Emitting Diode) or other suitable displaytechnology for conveying images to an end user of the communicationdevice 1000. In an embodiment where the display 1010 is touch-sensitive,a portion or all of the keypad 1008 can be presented by way of thedisplay 1010 with navigation features.

The display 1010 can use touch screen technology to also serve as a userinterface for detecting user input. As a touch screen display, thecommunication device 1000 can be adapted to present a user interfacewith graphical user interface (GUI) elements that can be selected by auser with a touch of a finger. The touch screen display 1010 can beequipped with capacitive, resistive or other forms of sensing technologyto detect how much surface area of a user's finger has been placed on aportion of the touch screen display. This sensing information can beused to control the manipulation of the GUI elements or other functionsof the user interface. The display 1010 can be an integral part of thehousing assembly of the communication device 1000 or an independentdevice communicatively coupled thereto by a tethered wireline interface(such as a cable) or a wireless interface.

The UI 1004 can also include an audio system 1012 that utilizes audiotechnology for conveying low volume audio (such as audio heard inproximity of a human ear) and high volume audio (such as speakerphonefor hands free operation). The audio system 1012 can further include amicrophone for receiving audible signals of an end user. The audiosystem 1012 can also be used for voice recognition applications. The UI1004 can further include an image sensor 1013 such as a charged coupleddevice (CCD) camera for capturing still or moving images.

The power supply 1014 can utilize common power management technologiessuch as replaceable and rechargeable batteries, supply regulationtechnologies, and/or charging system technologies for supplying energyto the components of the communication device 1000 to facilitatelong-range or short-range portable applications. Alternatively, or incombination, the charging system can utilize external power sources suchas DC power supplied over a physical interface such as a USB port orother suitable tethering technologies.

The location receiver 1016 can utilize location technology such as aglobal positioning system (GPS) receiver capable of assisted GPS foridentifying a location of the communication device 1000 based on signalsgenerated by a constellation of GPS satellites, which can be used forfacilitating location services such as navigation. The motion sensor1018 can utilize motion sensing technology such as an accelerometer, agyroscope, or other suitable motion sensing technology to detect motionof the communication device 1000 in three-dimensional space. Theorientation sensor 1020 can utilize orientation sensing technology suchas a magnetometer to detect the orientation of the communication device1000 (north, south, west, and east, as well as combined orientations indegrees, minutes, or other suitable orientation metrics).

The communication device 1000 can use the transceiver 1002 to alsodetermine a proximity to a cellular, Wi-Fi, Bluetooth®, or otherwireless access points by sensing techniques such as utilizing areceived signal strength indicator (RSSI) and/or signal time of arrival(TOA) or time of flight (TOF) measurements. The controller 1006 canutilize computing technologies such as a microprocessor, a digitalsignal processor (DSP), programmable gate arrays, application specificintegrated circuits, and/or a video processor with associated storagememory such as Flash, ROM, RAM, SRAM, DRAM or other storage technologiesfor executing computer instructions, controlling, and processing datasupplied by the aforementioned components of the communication device1000.

Other components not shown in FIG. 10 can be used in one or moreembodiments of the subject disclosure. For instance, the communicationdevice 1000 can include a reset button (not shown). The reset button canbe used to reset the controller 1006 of the communication device 1000.In yet another embodiment, the communication device 1000 can alsoinclude a factory default setting button positioned, for example, belowa small hole in a housing assembly of the communication device 1000 toforce the communication device 1000 to re-establish factory settings. Inthis embodiment, a user can use a protruding object such as a pen orpaper clip tip to reach into the hole and depress the default settingbutton. The communication device 1000 can also include a slot for addingor removing an identity module such as a Subscriber Identity Module(SIM) card. SIM cards can be used for identifying subscriber services,executing programs, storing subscriber data, and so forth.

The communication device 1000 as described herein can operate with moreor less of the circuit components shown in FIG. 10. These variantembodiments can be used in one or more embodiments of the subjectdisclosure.

The communication device 1000 can be adapted to perform the functions ofdevices of FIGS. 1-2 and/or 5A-5B, the eNB 817, the evolved packet core840, or the neighbor relations manager/cell selection server 830 of FIG.8, as well as the IMS CDs 801-802 and PSTN CDs 803-805 of FIG. 8. Itwill be appreciated that the communication device 1000 can alsorepresent other devices that can operate in systems of FIGS. 1-2 and/or5A-5B, communication system 800 of FIG. 8 such as a gaming console and amedia player. In addition, the controller 1006 can be adapted in variousembodiments to perform the functions 862-866, respectively.

Upon reviewing the aforementioned embodiments, it would be evident to anartisan with ordinary skill in the art that said embodiments can bemodified, reduced, or enhanced without departing from the scope of theclaims described below.

For example, as 5G deployments move forward, another LTE-5G NR DCscenario is that 5G cell acts as an anchor cell. Any one or more of thevarious techniques disclosed herein can be extend to this scenario,e.g., by adding new attribute LTE-5G DC Preference IE to a 5G cellneighbor relation table and/or in association with a 5G-5G cell messageexchange. In at least some embodiments, the various techniques discloseherein can be applied to a 5G cell-5G cell dual connectivity anchor cellselection, e.g., to improve and/or otherwise optimize a 5G anchor cellselection. Alternatively or in addition, the various techniquesdisclosed herein can apply to anchor cell selection when both LTE-5G DCand 5G-5G DC are possible. For example, a DC capable UE can be moved tothe either an LTE anchor cell and/or a 5G anchor cell that can provide apreferred, e.g., optimal performance Alternatively or in addition, thetechniques disclosed herein can be applied to a scenario in which userdata aggregation occurs in a core network portion of the mobile network.For example, the anchor cell preference can be set or otherwiseestablished based on one or more of a carrier preference, a cell load,and the like. It is understood that the various techniques disclosedherein can be applied to dual connectivity between any type of cellular,e.g., LTE, 4G, 5G and any other type of network, e.g., Wi-Fi and/orother future technologies. In at least some embodiments, one or more ofthe techniques disclosed herein can be integrated with self-organizingnetwork (SON) to provide network automation and traffic optimization.Other embodiments can be used in the subject disclosure.

It should be understood that devices described in the exemplaryembodiments can be in communication with each other via various wirelessand/or wired methodologies. The methodologies can be links that aredescribed as coupled, connected and so forth, which can includeunidirectional and/or bidirectional communication over wireless pathsand/or wired paths that utilize one or more of various protocols ormethodologies, where the coupling and/or connection can be direct (e.g.,no intervening processing device) and/or indirect (e.g., an intermediaryprocessing device such as a router).

FIG. 11 depicts an exemplary diagrammatic representation of a machine inthe form of a computer system 1100 within which a set of instructions,when executed, may cause the machine to perform any one or more of themethods described above. One or more instances of the machine canoperate, for example, as the eNB 104, 202, 406, 408, the 5G-WAP 108, theconfiguration server 136, the cell selector 132, elements of the corenetwork 130, the UE 106, 201, the O&M system 206, the MeNB 504, 554, theSgNB 506, 556, the neighbor relations manager/cell selection server 830,the media processor 806 and other devices of FIGS. 1-5 and 8-10. In someembodiments, the machine may be connected (e.g., using a network 1126)to other machines. In a networked deployment, the machine may operate inthe capacity of a server or a client user machine in a server-clientuser network environment, or as a peer machine in a peer-to-peer (ordistributed) network environment.

The machine may comprise a server computer, a client user computer, apersonal computer (PC), a tablet, a smart phone, a laptop computer, adesktop computer, a control system, a network router, switch or bridge,or any machine capable of executing a set of instructions (sequential orotherwise) that specify actions to be taken by that machine. It will beunderstood that a communication device of the subject disclosureincludes broadly any electronic device that provides voice, video ordata communication. Further, while a single machine is illustrated, theterm “machine” shall also be taken to include any collection of machinesthat individually or jointly execute a set (or multiple sets) ofinstructions to perform any one or more of the methods discussed herein.

The computer system 1100 may include a processor (or controller) 1102(e.g., a central processing unit (CPU)), a graphics processing unit(GPU, or both), a main memory 1104 and a static memory 1106, whichcommunicate with each other via a bus 1108. The computer system 1100 mayfurther include a display unit 1110 (e.g., a liquid crystal display(LCD), a flat panel, or a solid state display). The computer system 1100may include an input device 1112 (e.g., a keyboard), a cursor controldevice 1114 (e.g., a mouse), a disk drive unit 1116, a signal generationdevice 1118 (e.g., a speaker or remote control) and a network interfacedevice 1120. In distributed environments, the embodiments described inthe subject disclosure can be adapted to utilize multiple display units1110 controlled by two or more computer systems 1100. In thisconfiguration, presentations described by the subject disclosure may inpart be shown in a first of the display units 1110, while the remainingportion is presented in a second of the display units 1110.

The disk drive unit 1116 may include a tangible computer-readablestorage medium 1122 on which is stored one or more sets of instructions(e.g., software 1124) embodying any one or more of the methods orfunctions described herein, including those methods illustrated above.The instructions 1124 may also reside, completely or at least partially,within the main memory 1104, the static memory 1106, and/or within theprocessor 1102 during execution thereof by the computer system 1100. Themain memory 1104 and the processor 1102 also may constitute tangiblecomputer-readable storage media.

Dedicated hardware implementations including, but not limited to,application specific integrated circuits, programmable logic arrays andother hardware devices can likewise be constructed to implement themethods described herein. Application specific integrated circuits andprogrammable logic array can use downloadable instructions for executingstate machines and/or circuit configurations to implement embodiments ofthe subject disclosure. Applications that may include the apparatus andsystems of various embodiments broadly include a variety of electronicand computer systems. Some embodiments implement functions in two ormore specific interconnected hardware modules or devices with relatedcontrol and data signals communicated between and through the modules,or as portions of an application-specific integrated circuit. Thus, theexample system is applicable to software, firmware, and hardwareimplementations.

In accordance with various embodiments of the subject disclosure, theoperations or methods described herein are intended for operation assoftware programs or instructions running on or executed by a computerprocessor or other computing device, and which may include other formsof instructions manifested as a state machine implemented with logiccomponents in an application specific integrated circuit or fieldprogrammable gate array. Furthermore, software implementations (e.g.,software programs, instructions, etc.) including, but not limited to,distributed processing or component/object distributed processing,parallel processing, or virtual machine processing can also beconstructed to implement the methods described herein. Distributedprocessing environments can include multiple processors in a singlemachine, single processors in multiple machines, and/or multipleprocessors in multiple machines. It is further noted that a computingdevice such as a processor, a controller, a state machine or othersuitable device for executing instructions to perform operations ormethods may perform such operations directly or indirectly by way of oneor more intermediate devices directed by the computing device.

While the tangible computer-readable storage medium 1122 is shown in anexample embodiment to be a single medium, the term “tangiblecomputer-readable storage medium” should be taken to include a singlemedium or multiple media (e.g., a centralized or distributed database,and/or associated caches and servers) that store the one or more sets ofinstructions. The term “tangible computer-readable storage medium” shallalso be taken to include any non-transitory medium that is capable ofstoring or encoding a set of instructions for execution by the machineand that cause the machine to perform any one or more of the methods ofthe subject disclosure. The term “non-transitory” as in a non-transitorycomputer-readable storage includes without limitation memories, drives,devices and anything tangible but not a signal per se.

The term “tangible computer-readable storage medium” shall accordinglybe taken to include, but not be limited to: solid-state memories such asa memory card or other package that houses one or more read-only(non-volatile) memories, random access memories, or other re-writable(volatile) memories, a magneto-optical or optical medium such as a diskor tape, or other tangible media which can be used to store information.Accordingly, the disclosure is considered to include any one or more ofa tangible computer-readable storage medium, as listed herein andincluding art-recognized equivalents and successor media, in which thesoftware implementations herein are stored.

Although the present specification describes components and functionsimplemented in the embodiments with reference to particular standardsand protocols, the disclosure is not limited to such standards andprotocols. Each of the standards for Internet and other packet switchednetwork transmission (e.g., TCP/IP, UDP/IP, HTML, HTTP) representexamples of the state of the art. Such standards are from time-to-timesuperseded by faster or more efficient equivalents having essentiallythe same functions. Wireless standards for device detection (e.g.,RFID), short-range communications (e.g., Bluetooth®, Wi-Fi, Zigbee®),and long-range communications (e.g., WiMAX, GSM, CDMA, LTE) can be usedby computer system 1100. In one or more embodiments, informationregarding use of services can be generated including services beingaccessed, media consumption history, user preferences, and so forth.This information can be obtained by various methods including userinput, detecting types of communications (e.g., video content vs. audiocontent), analysis of content streams, and so forth. The generating,obtaining and/or monitoring of this information can be responsive to anauthorization provided by the user. In one or more embodiments, ananalysis of data can be subject to authorization from user(s) associatedwith the data, such as an opt-in, an opt-out, acknowledgementrequirements, notifications, selective authorization based on types ofdata, and so forth.

The illustrations of embodiments described herein are intended toprovide a general understanding of the structure of various embodiments,and they are not intended to serve as a complete description of all theelements and features of apparatus and systems that might make use ofthe structures described herein. Many other embodiments will be apparentto those of skill in the art upon reviewing the above description. Theexemplary embodiments can include combinations of features and/or stepsfrom multiple embodiments. Other embodiments may be utilized and derivedtherefrom, such that structural and logical substitutions and changesmay be made without departing from the scope of this disclosure. Figuresare also merely representational and may not be drawn to scale. Certainproportions thereof may be exaggerated, while others may be minimizedAccordingly, the specification and drawings are to be regarded in anillustrative rather than a restrictive sense.

Although specific embodiments have been illustrated and describedherein, it should be appreciated that any arrangement which achieves thesame or similar purpose may be substituted for the embodiments describedor shown by the subject disclosure. The subject disclosure is intendedto cover any and all adaptations or variations of various embodiments.Combinations of the above embodiments, and other embodiments notspecifically described herein, can be used in the subject disclosure.For instance, one or more features from one or more embodiments can becombined with one or more features of one or more other embodiments. Inone or more embodiments, features that are positively recited can alsobe negatively recited and excluded from the embodiment with or withoutreplacement by another structural and/or functional feature. The stepsor functions described with respect to the embodiments of the subjectdisclosure can be performed in any order. The steps or functionsdescribed with respect to the embodiments of the subject disclosure canbe performed alone or in combination with other steps or functions ofthe subject disclosure, as well as from other embodiments or from othersteps that have not been described in the subject disclosure. Further,more than or less than all of the features described with respect to anembodiment can also be utilized.

Less than all of the steps or functions described with respect to theexemplary processes or methods can also be performed in one or more ofthe exemplary embodiments. Further, the use of numerical terms todescribe a device, component, step or function, such as first, second,third, and so forth, is not intended to describe an order or functionunless expressly stated so. The use of the terms first, second, thirdand so forth, is generally to distinguish between devices, components,steps or functions unless expressly stated otherwise. Additionally, oneor more devices or components described with respect to the exemplaryembodiments can facilitate one or more functions, where the facilitating(e.g., facilitating access or facilitating establishing a connection)can include less than every step needed to perform the function or caninclude all of the steps needed to perform the function.

In one or more embodiments, a processor (which can include a controlleror circuit) has been described that performs various functions. Itshould be understood that the processor can be multiple processors,which can include distributed processors or parallel processors in asingle machine or multiple machines. The processor can be used insupporting a virtual processing environment. The virtual processingenvironment may support one or more virtual machines representingcomputers, servers, or other computing devices. In such virtualmachines, components such as microprocessors and storage devices may bevirtualized or logically represented. The processor can include a statemachine, application specific integrated circuit, and/or programmablegate array including a Field PGA. In one or more embodiments, when aprocessor executes instructions to perform “operations”, this caninclude the processor performing the operations directly and/orfacilitating, directing, or cooperating with another device or componentto perform the operations.

It should be appreciated that the techniques disclosed herein can beused to dynamically select LTE anchor cells for LTE-5G Dual Connectivityfunctions by adding a new “LTE-5G NR DC Preference” IE in neighborrelation table and to an X2-AP message. It is understood thatapplication of the disclosed techniques improves LTE-5G NR DCperformance, e.g., by enabling the DC in a preferred, e.g., the bestsuitable LTE cell. It is understood further that application of thedisclosed techniques improve network resource utilization and/orselection for DC anchor cell. Alternatively or in addition, applicationof the disclosed techniques reduces 5G introduction cost and/or anyrelated impact on existing and/or planned LTE cell network resources,e.g., according to one or more processing power, backhaul requirements,and the like. Application of one or more of the various disclosedtechniques can implement LTE-5G DC UE in a manner that extends and/orotherwise maximizes DC utilization and improves performance.

The Abstract of the Disclosure is provided with the understanding thatit will not be used to interpret or limit the scope or meaning of theclaims. In addition, in the foregoing Detailed Description, it can beseen that various features are grouped together in a single embodimentfor the purpose of streamlining the disclosure. This method ofdisclosure is not to be interpreted as reflecting an intention that theclaimed embodiments require more features than are expressly recited ineach claim. Rather, as the following claims reflect, inventive subjectmatter lies in less than all features of a single disclosed embodiment.Thus the following claims are hereby incorporated into the DetailedDescription, with each claim standing on its own as a separately claimedsubject matter.

What is claimed is:
 1. A system, comprising: a processing systemincluding a processor; and a memory that stores executable instructionsthat, when executed by the processing system, facilitate performance ofoperations, the operations comprising: ranking a plurality ofneighboring cells of a mobile cellular network according to dualconnectivity capability information obtained via configuration updatemessages, resulting in a dual connectivity ranking of the plurality ofneighboring cells; identifying a target cell of the plurality ofneighboring cells according to the dual connectivity ranking; andidentifying a dual connectivity capability of a mobile device, wherein adual connectivity service is initiated according to the dualconnectivity ranking, and wherein the dual connectivity servicecomprises exchanging user plane messages between the mobile device, amaster cell and a secondary cell of the mobile cellular network.
 2. Thesystem of claim 1, wherein the target cell comprises the master cell,and wherein the dual connectivity service is initiated via the targetcell based on the dual connectivity capability of the mobile device. 3.The system of claim 1, wherein the operations further comprise receivingthe configuration update messages from the plurality of neighboringcells.
 4. The system of claim 1, wherein a neighbor relation associatedwith the target cell and another one of the plurality of neighboringcells includes a dual connectivity preference.
 5. The system of claim 4,wherein the dual connectivity preference corresponds to one of aplurality of preference levels.
 6. The system of claim 4, wherein aplurality of neighbor relations associated with the target cell and eachof the other cells of the plurality of neighboring cells respectivelyare arranged in a neighbor relations table, and wherein the neighborrelations table is updated in accordance with the configuration updatemessages.
 7. The system of claim 6, wherein each of the plurality ofneighbor relations comprises a dual connectivity rating.
 8. The systemof claim 1, wherein the configuration update messages comprise apeer-to-peer message from a first evolved node B communications node toa second evolved node B communications node.
 9. The system of claim 8,wherein the peer-to-peer message includes a dual connectivitypreference.
 10. A method comprising: ranking, by a processing systemincluding a processor, a plurality of neighboring cells of a mobilecellular network according to dual connectivity capability informationobtained via configuration update messages, resulting in a dualconnectivity ranking of the plurality of neighboring cells; andidentifying a dual connectivity capability of a mobile device, wherein adual connectivity service is initiated according to the dualconnectivity ranking, and wherein the dual connectivity servicecomprises exchanging user plane messages between the mobile device, amaster cell and a secondary cell of the mobile cellular network.
 11. Themethod of claim 10, further comprising: receiving, by the processingsystem, the configuration update messages from the plurality ofneighboring cells; and identifying, by the processing system, a targetcell of the plurality of neighboring cells according to the dualconnectivity ranking.
 12. The method of claim 11, wherein the targetcell comprises the master cell, and wherein the dual connectivityservice is initiated via the target cell based on the dual connectivitycapability of the mobile device.
 13. The method of claim 11, wherein aneighbor relation associated with the target cell and another one of theplurality of neighboring cells includes a dual connectivity preference.14. The method of claim 13, wherein the dual connectivity preferencecorresponds to one of a plurality of preference levels.
 15. The methodof claim 10, wherein the configuration update messages comprise apeer-to-peer message from a first evolved node B communications node toa second evolved node B communications node.
 16. A machine-readablemedium comprising executable instructions that, when executed by aprocessing system including a processor, facilitate performance ofoperations, comprising: ranking a plurality of neighboring cells of amobile cellular network according to dual connectivity capabilityinformation obtained via configuration update messages, resulting in adual connectivity ranking of the plurality of neighboring cells;identifying a target cell of the plurality of neighboring cells; andidentifying a dual connectivity capability of a mobile device, wherein adual connectivity service is initiated according to the dualconnectivity ranking, and wherein the dual connectivity servicecomprises exchanging user plane messages between the mobile device, amaster cell and a secondary cell of the mobile cellular network.
 17. Themachine-readable medium of claim 16, wherein the target cell isidentified according to the dual connectivity ranking, and wherein thedual connectivity service is initiated via the target cell based on thedual connectivity capability of the mobile device.
 18. Themachine-readable medium of claim 16, wherein a neighbor relationassociated with the target cell and another one of the plurality ofneighboring cells includes a dual connectivity preference.
 19. Themachine-readable medium of claim 18, wherein the dual connectivitypreference corresponds to one of a plurality of preference levels. 20.The machine-readable medium of claim 16, wherein the configurationupdate messages comprise a peer-to-peer message from a first evolvednode B communications node to a second evolved node B communicationsnode.